Skip to content

feat: open app links like slack:// in the service they belong to - #2598

Open
eXistenZNL wants to merge 3 commits into
ferdium:developfrom
eXistenZNL:feat/open-app-links
Open

eXistenZNL wants to merge 3 commits into
ferdium:developfrom
eXistenZNL:feat/open-app-links

Conversation

@eXistenZNL

@eXistenZNL eXistenZNL commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Pre-flight Checklist

Please ensure you've completed all of the following.

Description of Change

This PR lets Ferdium open the app links of a service, like the slack:// link behind the "Open in app" button on a Slack web page, and lets each recipe decide which links are its own.

  • Ferdium now picks up any scheme:// link it is launched with, except its own ferdium:// deep links.
  • Recipes get a resolveLink(link, context) method. Ferdium asks the recipe of each displayed service, in sidebar order, whether a link is its own; the recipe returns the URL its service should load, or null. The base class returns null, so existing recipes keep working. When no recipe claims an http(s) link, Ferdium falls back to the same host matching as in feat: open http(s) links in the service they belong to #2597.
  • A recipe's webview.js can store details the page knows and Ferdium doesn't with Ferdium.setLinkContext({ ... }). Ferdium saves them with the service, only when they change, and passes them to resolveLink. Slack uses this to recognize which workspace a slack:// link is meant for.
  • Recipes list the app link protocols they handle in config.protocols, for example ["slack"].
  • A new setting, Open app links (like slack://) in Ferdium, registers Ferdium as the handler for the protocols of the recipes of the user's services. It is off by default, so Ferdium never takes over links from a native app the user still uses. Electron can't unregister a protocol handler on Linux, so the help text there points to xdg-mime. The setting is hidden on macOS, where an app can only handle the protocols listed in its Info.plist at build time; that will be a separate PR.
  • docs/OPENING_LINKS.md describes how a link travels through Ferdium and what a recipe can do.

This builds on #2597, so this PR also contains its commits until #2595 and #2597 are merged.

Part of a Larger Feature

This PR is part of a larger feature: letting Ferdium open links in the service they belong to, so it behaves more like the native apps of those services. That covers web links (for example a Slack permalink handed to Ferdium by a link router) and the app links of a service (for example the slack:// link behind the "Open in app" button on a Slack web page). Each recipe decides which links are its own, so a service can add support for its links without changes to Ferdium itself. App links can be enabled on Linux and Windows; macOS will follow in a later PR.

The feature is split up so each part can be reviewed on its own:

  1. fix: handle deep links on Linux #2595
  2. fix: don't open a window in a second instance #2596
  3. feat: open http(s) links in the service they belong to #2597 (builds on 1)
  4. feat: open app links like slack:// in the service they belong to #2598 (builds on 3) 👈 You are here
  5. feat: open links and app links in Slack and WhatsApp ferdium-recipes#761 (needs 4)

Motivation and Context

Ferdium handles a ton of services for me; with this change it can behave much more like the various native apps that exist for each service. Having this feature makes the whole process of getting a link into Ferdium (where you are logged in to a service) much more integrated.

Checklist

  • My pull request is properly named
  • The changes respect the code style of the project (pnpm prepare-code)
  • pnpm test passes
  • I tested/previewed my changes locally

Release Notes

New setting to let Ferdium open the app links of your services, like slack://.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant